@fluidframework/datastore-definitions
Advanced tools
Interface IFluidDataStoreRuntime specifies the data store developer API.
IFluidDataStoreRuntimeTODO: The full set of functionality is under review
Signals provide a transient data channel for data (any serializable payload) that doesn't need to be persisted in the op stream. Use signals where possible to avoid storing unnecessary ops, e.g. to transmit presence status during a collaborative session.
Signals are not persisted, ordered, or guaranteed. If a client is behind, the op state can be behind the signal state. For this reason people usually stick the currentSeq on the signal, so other clients can wait to process if they are behind.
You can send a signal via the container or data store runtime. The container will emit the signal event on all signals, but a data store will emit the signal event only on signals emitted on that data store runtime.
FAQs
Fluid data store definitions
The npm package @fluidframework/datastore-definitions receives a total of 5,843 weekly downloads. As such, @fluidframework/datastore-definitions popularity was classified as popular.
We found that @fluidframework/datastore-definitions demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 0 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Research
Socket researchers have discovered malicious npm packages targeting crypto developers, stealing credentials and wallet data using spyware delivered through typosquats of popular cryptographic libraries.
Security News
Socket's package search now displays weekly downloads for npm packages, helping developers quickly assess popularity and make more informed decisions.
Security News
A Stanford study reveals 9.5% of engineers contribute almost nothing, costing tech $90B annually, with remote work fueling the rise of "ghost engineers."